Databricks: Support Timetravel With "VERSION AS OF" #2155
Merged
+23
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
because now we can version by more than just timestamps
Contributor
Author
|
@iffyio I would love a review if you have time. |
iffyio
approved these changes
Jan 20, 2026
Contributor
iffyio
left a comment
iffyio
left a comment
There was a problem hiding this comment.
LGTM! Thanks @JamesVorder!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for Databricks' version-based time travel. This is a next step toward resolving #2006, following #2134.
The following is now supported:
Note: This PR makes a couple opinionated changes:
VERSION AS OFsyntax for all dialects that support time travel, regardless of downstream support for that syntax. (Consistent with guidance given here.)supports_timestamp_versioning-->supports_table_versioning, since we now support table versioning by something other than a timestamp.